Resideo's priority endpoint reports a room-level average temperature (roomAvgTemp) alongside the per-accessory temperature already exposed as Room Temperature. This was parsed but never surfaced. Adds it as a sibling entry to the existing Room Humidity sensor, which already uses the same room-level (not accessory-level) value.

Proposed change

Resideo's priority endpoint reports a room-level average temperature
(roomAvgTemp/avgTemperature) alongside the per-accessory temperature already
exposed as Room Temperature. This was parsed but never surfaced. Adds it as a
sibling entry to the existing Room Humidity sensor, which already uses the same
room-level (not accessory-level) value.

Dependency note: this needs both #177022 (coordinator actually fetching room data)
and the pending aiolyric field-name fix (room_avg_temp currently reads the wrong
JSON key) to show real data. Safe to merge independently — it'll just report
unavailable until both land, same as the existing Room Humidity sensor already
does today.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• [x ] New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Room sensor accessories (Honeywell Home RCHTSENSOR) paired to a T9/T10 thermostat are not being surfaced as entities #177010, Fix Lyric room sensor/priority data being silently skipped for T9/T10 thermostats #177022
• Companion library fix (required for this sensor to report real data): aiolyric PR fixing room_avg_temp's JSON key (part of timmo001/aiolyric#165)
• Link to documentation pull request: Lyric binary sensor and new sensors docs home-assistant.io#46986
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• [ x] I understand the code I am submitting and can explain how it works.
• [ x] The code change is tested and works locally.
• [ x] Local tests pass. Your PR cannot be merged unless tests pass
• [x ] There is no commented out code in this PR.
• [ x] I have followed the development checklist
• [x ] I have followed the perfect PR recommendations
• [ x] The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• [ x] Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io
  Link to documentation pull request: Lyric binary sensor and new sensors docs home-assistant.io#46986

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.